-
Notifications
You must be signed in to change notification settings - Fork 13k
chore: Improper calls to Meteor.userId() in React components
#36775
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
Looks like this PR is not ready to merge, because of the following issues:
Please fix the issues and try again If you have any trouble, please check the PR guidelines |
|
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## develop #36775 +/- ##
========================================
Coverage 66.09% 66.10%
========================================
Files 3298 3298
Lines 110881 110881
Branches 21031 21032 +1
========================================
+ Hits 73290 73295 +5
+ Misses 34915 34912 -3
+ Partials 2676 2674 -2
Flags with carried forward coverage won't be shown. Click here to find out more. 🚀 New features to boost your workflow:
|
4fdd67e to
2f4803a
Compare
dougfabris
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.

Proposed changes (including videos or screenshots)
It replaces calls to
Meteor.userId()in React components instead of relying onuseUserId().Issue(s)
ARCH-1786
Steps to test or reproduce
Further comments